I'm using the progressStart, progressStep, and progressMessage functions to create a progress bar for a metrics collection script we use. The progressStep gets incremented for each module that is processed. The progressMessage is updated for every object (1 of n) and every module. |
Re: Progress Bar |
Re: Progress Bar OurGuest - Mon Sep 26 16:25:51 EDT 2011 |
Re: Progress Bar I had similar no-luck as you experienced and ended up coding a separate program, run from another DOORS client, that would tell the 1st DOORS client to stop working and come to a gracefull end. The "for module" loop would therefore have a "did the other dude ask me to stop" check. Haven't used that in a few years. I think this is similar to my label DBE 'status' that I'd update. It would update for a while and then stop updating; and I'm thinking your progress bar is doing the same thing. Don't know why. If I were determined I would try some of the following: >> put a "sleep_(X)" command before the progress check; where X is perhaps '10' milliseconds. Maybe that will jar it up enough to become responsive. >> put a "sleep_(X)" command after every progress step command. >> put far less updates, as I'm feeling like its the number of updates that puts it into limbo, not how long you've been running. >> implement a 'timer' DBE that auto-checks if progress has been cancelled, and sets a global flag.
|